Skip to main content

Overview

The IAU2000 WKT system provides a comprehensive set of coordinate reference systems (CRS) for planetary bodies, similar to EPSG codes for Earth. These projections implement IAU (International Astronomical Union) standards for planetary cartography and can be used directly with GDAL tools.
These projections enable standardized spatial reference systems across planetary science applications, from Mars rovers to outer planet moons.

Available Versions

IAU2000

Based on the 2002 IAU/IAG report (Seidelmann et al.)

IAU2009

Based on the 2011 IAU report (Archinal et al.)

IAU2015

Based on the 2018 IAU report (Archinal et al.) - Most current
Each version reflects updated planetary body parameters (radii, rotation elements) from the respective IAU Working Group reports.

Code Structure

Projection codes follow a systematic pattern:

Examples

Projection Code Suffixes

Ocentric vs. Ographic:
  • Ocentric: Planetocentric latitudes (angle from center)
  • Ographic: Planetographic latitudes (angle from surface normal)

Using Projections from GitHub

GDAL can read projections directly from the raw GitHub repository using curl:

Reproject with gdalwarp

Inspect Projection

URL Encoding: Spaces in filenames must be encoded as %20 in URLs.

Use HTTPS

Both http and https protocols work:

Generating Custom WKT Files

The create_IAU2000_wkt_v3.py script generates WKT projection definitions from CSV radius tables.

Usage

Parameters

string
required
CSV file with NAIF IDs and planetary radii. Available versions:
  • naifcodes_radii_m_wAsteroids_IAU2000.csv
  • naifcodes_radii_m_wAsteroids_IAU2009.csv
  • naifcodes_radii_m_wAsteroids_IAU2015.csv
string
Output WKT file. If omitted, writes to stdout.

Input CSV Format

Example Output WKT

Supported Planetary Bodies

The system includes projections for:
  • Mercury (199)
  • Venus (299)
  • Earth (399)
  • Mars (499)
  • Moon/Luna (301)
  • Phobos (401), Deimos (402)
  • Jovian moons: Io, Europa, Ganymede, Callisto, Amalthea, Thebe, Adrastea, Metis
  • Saturnian moons: Titan, Rhea, Iapetus, Dione, Tethys, Enceladus, Mimas, Hyperion, Phoebe, Janus, Epimetheus, and more
  • Uranian moons: Titania, Oberon, Umbriel, Ariel, Miranda
  • Neptunian moons: Triton, Proteus, Nereid
  • Plutonian moons: Charon
  • Ceres, Vesta, Pallas, Lutetia, Ida, Gaspra, Eros, Mathilde, Steins
  • Comets: Halley, Borrelly, Tempel 1, Hartley 2, Wild 2
  • Jupiter (599)
  • Saturn (699)
  • Uranus (799)
  • Neptune (899)
  • Pluto (999)

Coordinate Reference System Details

Datum Definition

Each planetary body uses a triaxial ellipsoid (or sphere) defined by:
  • Semimajor axis (a): Equatorial radius
  • Semiminor axis (c): Polar radius
  • Flattening: f = (a - c) / a or 1/f for SPHEROID definition

Triaxial Bodies

For bodies where a ≠ b ≠ c, the mean radius is used:

Projection Types

Static Projections (10-29)

Fixed parameters, specific central meridians:
  • Equirectangular: Simple cylindrical, lat/lon = x/y
  • Sinusoidal: Equal-area, good for global mosaics
  • Stereographic: Polar projections (North/South)
  • Mollweide: Equal-area elliptical
  • Robinson: Compromise projection

AUTO Projections (60-83)

Dynamic parameters that can be adjusted:
  • Sinusoidal AUTO (60, 61)
  • Stereographic AUTO (62, 63)
  • Transverse Mercator AUTO (64, 65)
  • Orthographic AUTO (66, 67)
  • Equidistant Cylindrical AUTO (68, 69)
  • Lambert Conformal Conic AUTO (70, 71)
  • Lambert Azimuthal Equal Area AUTO (72, 73)
  • Mercator AUTO (74, 75)
  • Albers AUTO (76, 77)
  • Oblique Cylindrical Equal Area AUTO (78, 79)
  • Mollweide AUTO (80, 81)
  • Robinson AUTO (82, 83)
AUTO projections allow custom central meridians and standard parallels while maintaining body-specific datum parameters.

Integration with GDAL

Assign Projection to Unprojected Data

Reproject Between Systems

Extract Projection Info

Script Location

Pre-generated Files

The repository includes pre-generated WKT files:
And individual .prj files for each body:

PostGIS Integration

The repository includes experimental PostGIS scripts:
These generate SQL INSERT statements for loading IAU projections into PostGIS spatial_ref_sys table.
Untested: PostGIS scripts are experimental and may require modification for your database version.

IAU Standards References

Seidelmann, P.K., et al. (2002). “Report of the IAU/IAG Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites: 2000,” Celestial Mechanics and Dynamical Astronomy, v.82, Issue 1, pp. 83-111.
Archinal, B.A., et al. (2011). “Report of the IAU Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites: 2009,” Celestial Mechanics and Dynamical Astronomy, v.109, Issue 2, pp. 101-135.
Archinal, B.A., et al. (2018). “Report of the IAU Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellites: 2015,” Celestial Mechanics and Dynamical Astronomy, 130: 22. https://doi.org/10.1007/s10569-017-9805-5

Best Practices

1

Choose IAU Version

Use IAU2015 for most current radii and parameters. Use older versions only for compatibility with existing datasets.
2

Select Projection

Choose based on application:
  • Global mosaics: Sinusoidal or Mollweide (equal-area)
  • Polar regions: Stereographic (18-21)
  • Regional mapping: Equirectangular (10-13) or AUTO projections
  • Web maps: Equirectangular at equator
3

Ocentric vs. Ographic

  • Ocentric: Standard for most planetary work, consistent with SPICE kernels
  • Ographic: Traditional for mapping, matches surface tangent
4

Document Metadata

Always record which IAU version and projection code you use in dataset metadata.

Contact

Trent Hare
Astrogeology, U.S. Geological Survey
thare@usgs.gov

Additional Resources